home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Almathera Ten Pack 3: CDPD 3
/
Almathera Ten on Ten - Disc 3: CDPD3.iso
/
scope
/
026-050
/
scopedisk33
/
rxenv
/
readme
< prev
next >
Wrap
Text File
|
1995-03-18
|
3KB
|
59 lines
Hello All!
The AREXX programs and other stuff included in this ARC are public domain,
and you may do with them as you will. Or, you can send me a couple of
thousand bucks and never change them at all! Your Choice! <grin>
What you need to do before you can use my stuff:
1) I set up the following assigns, and you will need to assign these
logical devices also (talking strictly Lattice C here! I have never even
seen a Manx compiler!):
Assign LC: SYS:Lattice/C
Assign LINK: LC:
Assign QUAD: RAM:
Assign LIB: SYS:Lattice/Lib
Assign INCLUDE: SYS:Lattice/IncludeFiles
Assign Source: SYS:Source
Assign Obj: Source:Obj
2) Purchase TxEd Plus, and AREXX. I highly recommend WShell also!
What they are:
1) RXCOMP - After you have finished making changes to your source code,
you can select the "Run Compile" option in the User menu. "Run Compile"
accesses compile.txed which will auto-magically save your source, and then
call RXCOMP with the name of your file. I did it this way so that you can
type "RXCOMP foo" in WShell (another great program by Mr. Hawes!) and
compile foo, or load foo into TxEd+ and compile it there. The difference
is that between AREXX programs with extention ".rexx" and those with
".txed".
2) RXLINK - Basically, all RXLINK does is call BLINK using the "with"
file "main.w". All the "Run Link" menu option does is to call link.txed
which calls RXLINK :). I did it this way in case I get a brainstorm on how
to set up link.txed to figure out WHICH "with" file I want to link with!
3) RXMAKE - By comparing the dates on source files and object files,
RXMAKE figures out if you have changed a source. It will then create an
execute file containing the lines "rxcomp foo-1" ... "rxcomp foo-y" and
tack on the line "rxlink main" at the end. I added the option to type
"RXMAKE ALL", which will search your Source: directory and set up to
compile ALL the .c files present in Source:.
Known Bugs:
Basically, I only have one bug note to report, and that concerns the use of
TxEd Plus. I have noticed that if you have more that one TxEd+ editing
window open, and you close any one of them, the menu alterations created
in the startup.txed file go out the window (sorry, but that pun was
intended! :).
This means that you will need to open up a command window "hit the HELP
key!" and type "startup". This will re-configure you back to the way you
originally began your editing session.